Summary

• This work is behind a feature toggle (flipper): YES: The feature that this documentation is for is behind a feature flag.
• (Summarize the changes that have been made to the platform): This adds swagger docs for RepresentationManagement::V0::AccreditedEntitiesForAppointController.
• (If bug, how to reproduce)
• (What is the solution, why is this the solution?): We were encouraged to have swagger docs for all of our endpoints before release.
• (Which team do you work for, does your team own the maintenance of this component?): FAR/ARM. We own the maintenance.
• (If introducing a flipper, what is the success criteria being targeted?)

Related issue(s)

• Add Swagger Documentation for RepresentationManagement::V0::AccreditedEntitiesForAppointController va.gov-team#91484
• Link to previous change of the code/bug (if applicable)
• Link to epic if not included in ticket

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change: This endpoint wasn't documented.
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing: Start the server and point a Swagger-UI at http://localhost:3000/representation_management/v0/apidocs. You'll be able to see these docs and all our others there.
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?

Screenshots

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas): This just impacts the documentation for the representation_management module.

Acceptance criteria

• I added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation) This PR is the documentation.
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature